Files modified in the past should not trigger a fingerprint change
authorJake Goulding <jake.goulding@integer32.com>
Thu, 14 Jul 2016 23:17:08 +0000 (19:17 -0400)
committerJake Goulding <jake.goulding@integer32.com>
Wed, 27 Jul 2016 23:52:27 +0000 (19:52 -0400)
commitbcbe0c0b00b29ab301b58cf0045a99f35917bdf2
tree594bfddce78a062c8b9fae74c4ae76e29b0fe9d2
parenta7c457e8033c2b0d0b107ed2f14d39315393aff2
Files modified in the past should not trigger a fingerprint change

Previously, we would bail from the fingerprint computation if the old
and new mtimes had changed in *any* way. This caused some issues of
rebuilding with filesystems that do not preserve nanosecond
granularity (#2874).
src/cargo/ops/cargo_rustc/fingerprint.rs